System, method, and app for managing waste services

ABSTRACT

A system is disclosed for providing a waste management app. The system may have a locating device disposed onboard a service vehicle and configured to generate a first signal indicative of a location of the service vehicle, an input device, and a controller. The controller may be configured to receive a route assignment including waste services to be performed by the service vehicle, and to track movement of the service vehicle during performance of the waste services based on the first signal. The controller may also be configured to provide a graphical user interface for display on the input device, listing the waste services from the route assignment to be performed by the service vehicle and showing a location of the service vehicle relative to at least one location at which the waste services are to be performed.

RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.15/420,962, filed on Jan. 31, 2017, which is a continuation of U.S.application Ser. No. 15/168,803, filed on May 31, 2016, now U.S. Pat.No. 9,574,892, issued Feb. 21, 2017, which is based on and claimspriority to U.S. Provisional Application Nos. 62/183,454 filed on Jun.23, 2015; 62/299,183 filed on Feb. 24, 2016; and 62/306,515 filed onMar. 10, 2016, the contents of all of which are expressly incorporatedherein by reference.

TECHNICAL FIELD

The present disclosure relates generally to an app (i.e., a downloadableself-contained software application) for use on a mobile device. Moreparticularly, the present disclosure relates to a system and method forproviding a waste management app that allows an operator of a servicevehicle to manage waste services.

BACKGROUND

Commercial and residential waste service providers typically dispatchservice vehicles to customer properties according to a predeterminedpickup schedule assigned to each service vehicle. The pickup schedulefor each service vehicle is often designed to provide waste services(e.g., to empty waste receptacles) within a particular geographical areaand at a particular frequency (e.g., once per week). After completion ofthe waste services, the service vehicle operator may report thecompletion to a back office, which updates the operator's schedule andan account record for the customer. Customers that subscribe to thesewaste services are then billed based on the account record. The operatorthen maneuvers the service vehicle to a next customer location forcompletion of additional waste services.

In some instances, it may be difficult to manage the pickup schedule foreach service vehicle. In particular, the pickup schedule can changefrequently, and include new customer locations and/or locations havingcomplex service requirements. In these instances, it can be difficultfor the service vehicle operator to determine which stops to make, theorder of the stops, the timing of the stops, etc. It can also bedifficult to find the new locations, to determine travel routes to newlocations, to manage instructions associated with required services ateach location, and to keep track of the completed services. No toolscurrently exist to help the service vehicle operator with these aspectsof waste management.

The disclosed system, method, and app are directed to overcoming one ormore of the problems set forth above and/or other problems of the priorart.

SUMMARY

In one aspect, the present disclosure is directed to a system forproviding a waste management app. The system may include a locatingdevice disposed onboard a service vehicle and configured to generate afirst signal indicative of a location of the service vehicle. The systemmay also include an input device, and a controller in communication withthe locating device and the input device. The controller may beconfigured to receive a route assignment including waste services to beperformed by the service vehicle, and to track movement of the servicevehicle during performance of the waste services based on the firstsignal. The controller may also be configured to provide a graphicaluser interface for display on the input device. The graphical userinterface may show a listing the waste services from the routeassignment to be performed by the service vehicle, and a location of theservice vehicle relative to at least one location at which the wasteservices are to be performed.

In another aspect, the present disclosure is directed to a method forproviding a waste management app. The method may include receiving aroute assignment including waste services to be performed by a servicevehicle, and tracking movement of the service vehicle during performanceof the waste services. The method may also include providing a graphicaluser interface for display to an operator of the service vehicle. Thegraphical user interface may list the waste services from the routeassignment to be performed by the service vehicle and show a location ofthe service vehicle relative to at least one location at which the wasteservices are to be performed.

In yet another aspect, the present disclosure is directed to anon-transitory computer readable medium containing computer-executableprogramming instructions for performing a method of providing a wastemanagement app. The method may include receiving a route assignmentincluding waste services to be performed by a service vehicle at aplurality of locations, and tracking movement of the service vehicleduring performance of the waste services. The method may also includeproviding a graphical user interface for display to an operator of theservice vehicle. The graphical user interface may list the wasteservices from the route assignment in an order to be performed by theservice vehicle, and show on a map a location of the service vehiclerelative to the plurality of locations at which the waste services areto be performed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective illustration of an exemplary disclosed wastemanagement environment;

FIG. 2 is a diagrammatic illustration of an exemplary disclosed systemthat may be used to manage the environment of FIG. 1; and

FIGS. 3-11 are diagrammatic illustrations of exemplary disclosedgraphical user interfaces that may be used to access the system of FIG.2.

DETAILED DESCRIPTION

FIG. 1 illustrates an exemplary waste management environment(“environment”) 10, at which one or more service vehicles 12 areproviding waste services. Environment 10 may include a retail store, afactory, a government building, a residential address, or anotherlocation having one or more receptacles 14 that require the service ofservice vehicle(s) 12. The service may include, for example, the removalof waste materials from inside of receptacle(s) 14, the replacement ofreceptacle(s) 14, and/or the placement of new or additional receptacles14.

Service vehicle 12 may take many different forms. In the example shownon the right in FIG. 1, service vehicle 12 is a hydraulically actuated,front-loading type of service vehicle. Specifically, service vehicle 12may include a bed 16 supported by a plurality of wheels 18, a cab 20located forward of bed 16, and a lifting device 22 extending forward ofcab 20. Lifting device 22 may consist of, among other things, one ormore lift arms 24 configured to engage and/or grasp receptacle 14, andone or more actuators 26 powered by pressurized oil to raise and tiltlift arms 24 (and receptacle 14) up past cab 20 to a dump location overbed 16. After dumping of receptacle 14, pressurized oil may be releasedfrom hydraulic actuator(s) 26 to allow lowering of lift arms 24 andreceptacle 14 back to the ground in front of service vehicle 12.

In other examples, lifting device 22 may be located to pick upreceptacles 14 from a side and/or a rear of service vehicle 12. In yetother examples, receptacles 14 may be manually lifted and dumped intobed 16. In any of these examples, bed 16 could be outfitted with acompactor (not shown) to compact the waste material after the materialis dumped into bed 16, and/or a door (not shown) configured to close anopening of bed 16 through which the waste material is dumped. Otherconfigurations may also be possible.

In the example shown on the left in FIG. 1, service vehicle 12 is ahydraulically actuated flatbed or roll-off type of service vehicle.Specifically, service vehicle 12 may include a bed 16 supported by aplurality of wheels 18, a cab 20 located forward of bed 16, and alifting device 22 extending rearward of cab 20. Lifting device 22 mayconsist of, among other things, one or more actuators 26 powered bypressurized oil to raise and tilt receptacle 14 up onto bed 16 fortransportation of receptacle 14 away from environment 10. After dumpingof receptacle 14 at a landfill (or swapping a full receptacle 14 for anempty receptacle 14), receptacle 14 may be returned to environment 10and lowered back to the ground behind service vehicle 12 (e.g., byreleasing pressurized oil from hydraulic actuator(s) 26).

As each service vehicle 12 moves about environment 10, a satellite 28 orother tracking device may communicate with an onboard controller 30(shown only in FIG. 2) to monitor the movements of service vehicle 12and the associated changes made to environment 10 (e.g., pickup,dumping, placement, etc.). As will be explained in more detail below,onboard controller 30, or a separate offboard controller 32 (e.g., acontroller 32 located in a back office 34 or other servicefacility—shown only in FIG. 2), may then manage future operations ofservice vehicle 12 (and other similar service vehicles 12) based onthese movements and changes.

Both of onboard and offboard controllers 30, 32 may include means formonitoring, recording, storing, indexing, processing, communicating,and/or controlling other onboard and/or offboard devices. These meansmay include, for example, a memory, one or more data storage devices, acentral processing unit, or any other components that may be used to runthe disclosed application. Furthermore, although aspects of the presentdisclosure may be described generally as being stored in memory, oneskilled in the art will appreciate that these aspects can be stored onor read from different types of computer program products orcomputer-readable media such as computer chips and secondary storagedevices, including hard disks, floppy disks, optical media, CD-ROM, orother forms of RAM or ROM.

As shown in FIG. 2, onboard controller 30 may form a portion of a wastemanagement system (“system”) 36 that is configured to track, assist,and/or control movements of service vehicle(s) 12 (shown only in FIG.1). In addition to onboard controller 30, system 36 may also include alocating device 38, and at least one of a manual input device 40 and asensor 42 mounted or otherwise located onboard each service vehicle 12.In some embodiments, system 36 includes both manual input device 40 andone or more sensors 42. In other embodiments, sensor 42 (and/or onboardcontroller 30) may be internal to manual input device 40. Onboardcontroller 30 may be in communication with each of these othercomponents and/or with onboard controller 32 at back office 34 (e.g.,via a communication device 44), and configured to determine, based onsignals from these components and based on other known informationstored in memory, the location of each service vehicle 12 andcharacteristics and locations of receptacles 14 being moved by and/or ina vicinity of each service vehicle 12.

Locating device 38 may be configured to generate signals indicative of ageographical position and/or orientation of service vehicle 12 relativeto a local reference point, a coordinate system associated withenvironment 10, a coordinate system associated with Earth, or any othertype of 2-D or 3-D coordinate system. For example, locating device 38may embody an electronic receiver configured to communicate withsatellites 28 (referring to FIG. 1), or a local radio or lasertransmitting system used to determine a relative geographical locationof itself. Locating device 38 may receive and analyze high-frequency,low-power radio or laser signals from multiple locations to triangulatea relative 3-D geographical position and orientation. In someembodiments, locating device 38 may also be configured to determine alocation and/or orientation of a particular part of service vehicle 12,for example of lift arms 24 (shown only in FIG. 1). Based on the signalsgenerated by locating device 38 and based on known kinematics of servicevehicle 12, onboard controller 30 may be able to determine in real time,the position, heading, travel speed, acceleration, and orientation ofservice vehicle 12 and lift arms 24. This information may then be usedby onboard and/or offboard controllers 30, 32 to update the locationsand conditions of service vehicle(s) 12 and/or receptacles 14 in anelectronic map or database of environment 10.

It is contemplated that locating device 38 may take another form, ifdesired. For example, locating device 38 could be an REID readerconfigured to interact with an RFID tag located within environment 10(e.g., at a customer location, on receptacle 14, etc.), or another typeof scanner configured to read another type of indicia (e.g., a barcode)within environment 10. Based on the reading of the RFID tag or otherindicia, the location and/or orientation of service vehicle 12 may belinked to the known location of the RFID tag or other indicia withinenvironment 10.

Manual input device 40 may provide a way for an operator of servicevehicle 12 to input information regarding observances made whiletraveling around environment 10. For example, the operator may be ableto enter a type and/or condition of waste observed at a particularlocation, an amount of waste in or around receptacle 14, a fill statusof a particular receptacle 14, a condition of receptacle 14, a locationof receptacle 14, and or other information about the receptacle andwaste engaged by, loaded into, or otherwise processed by service vehicle12. The information may be input in any number of ways, for example viaa cab-mounted touch screen interface, via one or more buttons, via akeyboard, via speech recognition, via a mobile device (e.g., asmartphone or tablet) carried by the operator, or in another mannerknown in the art. In some embodiments, the operator may also be able torespond to inquiries received via input device 40, if desired. Inaddition to receiving manual input from an operator, input device 40 mayalso be capable of displaying information, for example the electronicmap of environment 10, instructions from back office 34, scheduling,receptacle information (e.g., ID, configuration, location, weight,etc.), payload information (e.g., weight and/or volume), questions, etc.

In some embodiments, input device 40 may be configured to execute anapplication. For example, when input device 40 is a mobile device (forexample a smartphone), the application can be a mobile app (“app”). Anapp is an abbreviated term for a “software application”, which isdownloadable to and executable by a mobile device (e.g., a laptop, asmart phone, or a tablet). The disclosed waste management app canprovide a graphical user interface (GUI) configured to displayinformation about a waste handling operation to the operator of servicevehicle 12; and that receives input from the operator used to configureacquisition of operational data by sensor(s) 42, to transmit theoperational data to controllers 30, 32, to receive and displayinformation about a current operation (e.g., as monitored by sensor(s)42), etc.

Sensors 42 may be configured to monitor parameters associated with thewaste material loaded into service vehicle 12 and/or the associatedreceptacles 14 being moved by service vehicle 12 (e.g., moved by liftarms 24), and to generate corresponding signals indicative thereof. Eachof these sensors 42 may be any type of device known in the art, andlocated anywhere on or in service vehicle 12. In one example, sensor 42may embody a lift sensor, such as any one or more of a load cell, aforce gauge, a pressure sensor, a motion sensor, or another type of liftsensor associated directly with lift arms 24, with actuator(s) 26, withreceptacle 14, and/or with a strut 46 supporting bed 16. In thisexample, the signals generated by sensor(s) 42 may correspond withstrain on lift arms 24, with a force applied to lift arms 24 byactuator(s) 26, with a payload weight of bed 16, with a motion ofreceptacle 14, with a weight of waste contained inside receptacle 14,etc.

Alternatively, one or more sensors 42 may be associated with a powersource or drivetrain of service vehicle 12, and configured to generatesignals indicative of an amount of power used to propel service vehicle12, to drive the hydraulics of actuators 26, to move the in-bedcompactor, or to shut the associated door. Other types of sensors 42(e.g., cameras, spectrometers, IR sensors, RADAR sensors, LIDAR sensors,etc.) may also be utilized to determine characteristics (e.g., loadprofile, volume, and/or shape) of the waste material inside receptacles14 or of receptacles 14 themselves. In yet further examples, sensor 42could be an acoustic sensor (e.g., one or more microphones), anaccelerometer, or another similar type of sensor configured to detectengagement conditions and/or cycle completion of lift arms 24, thein-bed compactor, the door, etc. during lifting, dumping, and/or shakingof receptacle 14. Other types of sensors 42 may alternatively oradditionally be utilized. Signals generated by these sensors 42 may becommunicated to onboard and/or offboard controllers 30, 32, and theappropriate controller may use the signals to determine conditionssurrounding receptacles 14 (and/or the waste inside receptacles 14)before, during, and/or after servicing by service vehicle 12. Asdescribed above, any one or more of sensors(s) 42 may form an integralportion of input device 40 (e.g., the smartphone or tablet carried bythe operator) or be a standalone component in wired or wirelesscommunication with controllers 30, 32 and/or input device 40, asdesired.

Onboard controller 30 may be configured to manage communications betweenother onboard components and onboard controller 32 located at backoffice 34. For example, onboard controller 30 may receive signals fromlocating device 38, input device(s) 40, and sensor(s) 42, and correlatethe signals, filter the signals, buffer the signals, record the signals,or otherwise condition the signals before directing the signals offboardvia communication device 44.

Communication device 44 may be configured to facilitate communicationbetween onboard controller 30 and offboard controller 32. Communicationdevice 44 may include hardware and/or software that enable the sendingand/or receiving of data messages through a communications link. Thecommunications link may include satellite, cellular, infrared, radio,and any other type of wireless communications. Alternatively, thecommunications link may include electrical, optical, or any other typeof wired communications, if desired. In one embodiment, onboardcontroller 30 may be omitted, and offboard controller 32 may communicatedirectly with locating device 38, input device(s) 40, and/or sensor(s)42 via communication device 44, if desired. Other means of communicationmay also be possible.

Onboard and/or offboard controllers 30, 32, based on the informationreceived from onboard service vehicles 12 and also based on informationreceived from other sources (e.g., from the Internet, from input at backoffice 34, etc.), can be configured to execute instructions stored oncomputer readable medium to perform methods of waste management atenvironment 10. For example, onboard and/or offboard controllers 30, 32may be configured to monitor when service vehicle 12 is nearing a targetlocation (e.g., based on the known address and signals from locatingdevice 38), when service vehicle 12 has stopped, when service vehicle 12is servicing receptacle 14, when service vehicle 12 is filled with wasteto a maximum capacity, etc. This monitoring may then be used todetermine route assignments for service vehicle 12, determine businesscosts and efficiencies, determine service opportunities, make routeadjustments, etc.

FIGS. 3-11 represent exemplary Graphical User Interfaces (GUIs) that maybe shown in connection with the disclosed waste management app on anyinput device 40 for use by an operator of service vehicle 12 to accesssystem 36. FIGS. 3-11 will also be discussed in greater detail below tofurther illustrate the disclosed concepts.

INDUSTRIAL APPLICABILITY

The disclosed system, method, and app may be applicable to the wasteservice industry, where efficient management of waste services canaffect profitability for a provider. The disclosed system, method, andapp may provide a way for individual service vehicle operators tovisually receive the daily tasks assigned to a particular servicevehicle in an organized manner. For example, the disclosed system,method, and app may provide a graphical user interface (GUI) allowingthe operator to see a schedule of the daily tasks arranged in an orderthat reduces time, effort, and fuel, and also satisfies customerexpectations. The GUI provided by the disclosed app may also relay tothe operator visual directions to customer locations and specialinstructions for each location. In addition, the GUI may provide visualstatus indications associated with the daily tasks, and a way for theoperator to provide feedback or other input regarding the tasks, thecustomer locations, the service vehicle, the schedule, etc. ExemplaryGUIs associated with the disclosed app will now be described in detail,with reference to FIGS. 3-11.

During operation of system 36 a schedule of customer locations may begenerated at back office 34 (referring to FIG. 2) for each servicevehicle 12 (referring to FIG. 1) in the service fleet of a particularservice provider. The schedule may be created in any manner known in theart. For example, the schedule may be created based on contracts forservice, which detail geographical locations at which a particularcustomer desires particular waste services to be performed, a timing(e.g., date, day, time, and/or frequency) of the services, and detailsabout the services (e.g., a number, configuration, position, and/or sizeof receptacles 14 at the customer location that require service; a typeof waste; and/or instructions regarding access to receptacles 14). Inaddition, the schedules may be created based on the particular servicevehicles 12 that are available to perform the services. These detailsmay include a number, type, size, location, capacity, and availabilityof service vehicles 12. The contract and/or service vehicle informationmay be received directly from the customer(s), from representatives ofthe service provider of system 36, from service vehicles 12 (and/ortheir operators), and/or from an electronic data storage, memory, ordatabase of system 36. The assignments may be determined and/or assignedmanually (e.g., by a service representative) or automatically (e.g., byoffboard controller 32) using any strategy known in the art, andsubsequently relayed to the operator of each service vehicle 12 (e.g.,by way of communication device 44). Each route assignment may include aplurality of service stops, which are sequentially arranged and providedwith target times for completion of associated service tasks. The routeassignments may then be stored, for example within onboard controller30, and/or communicated to any of input devices 40.

FIG. 3 shows an exemplary GUI 300 that may be provided in connectionwith the disclosed app on any input device 40 (e.g., on a smartphonecarried by the operator of service vehicle 12) at start of a shift for aparticular operator within a particular service vehicle 12. In thisexample, GU 300 displays to the operator a corresponding routeassignment received from back office 34. The route assignment mayinclude a listing of scheduled stops provided in a particular order(e.g., a top-to-bottom order) that the operator should follow. Thelisting may include a name of each stop, an address of each stop, adesired service time for each stop, and instructions regardingparticular service tasks (e.g., pickup, empty, return, etc.) to beperformed at each stop. In addition, GUI 300 may display a visualindication as to which service tasks have been completed, and a mapshowing one or more stop locations relative to a current position ofservice vehicle 12 (obtained via location device 38).

In the example shown in FIG. 3, two stops are listed in the routeassigned to the operator of a particular service vehicle 12. The twostops include a first stop at John's Home and a second stop at Big JCoffee. It should be noted that each route assignment could include anynumber of stops. John's Home is shown as being located at 3300 HillviewAve and has a scheduled service time of 8:00 am. Big J. Coffee is shownas being located at 3500 Hillview Ave and has a later scheduled servicetime of 9:00 am. The service to be completed at John's Home is simply toempty an existing receptacle 14 into bed 16 of service vehicle 12; whilethe service to be completed at Big J Coffee is to pick up an existingreceptacle 14, take the receptacle 14 to a particular land fill (i.e.,to Landfill A), and then to return the empty receptacle 14 back to Big JCoffee. Other service tasks could also or alternatively be associatedwith each stop, as desired. The service at John's Home is shown ashaving been completed (e.g., with a checkmark).

The completion of service at a particular stop in an assigned route maybe confirmed manually and/or automatically, as desired. For example,upon completion of a particular service task at a particular location,the operator of service vehicle 12 may provide manual input indicativeof the completion to input device 40. This input could include, forexample, pressing of a button, touching of a screen (e.g., touching thecheckmark area shown in FIG. 3 at the left of “John's Home”), voicing anaudible command, etc. In other embodiments, however, completion of theparticular task could be automatically confirmed based on a trackedlocation, motion, and/or speed of service vehicle 12 (e.g., by detectinga stop at John's Home) performed by locating device 38; based on inputreceived from sensor(s) 42 (e.g., a detected increase in weight of bed16, a detected lifting/tilting motion of lift arms 24, a detected forceincrease of actuators 26, a detected acoustic signature associated withnormal lifting/tilting/dumping of receptacle 14, a scanned barcode ofreceptacle 14 located at John's Home, a captured image of John's Home,etc.); and/or based on other information.

After confirmation is received that waste services at a particular stopin the assigned route have been completed, the map shown in GUI 300 mayrepresent the relative location associated with a next stop in theroute. That is, after completion of a service task at one stop, thedisclosed app may cause the map to be automatically updated andcorrespond with the next stop. It is also contemplated that the operatormay manually request the relative location associated with anyparticular stop to be shown in the map of GUI 300, if desired,regardless of the status of a particular service task.

In one embodiment, the operator of service vehicle 12 may be able toobtain more detailed information about the next (or any selected) stopin the assigned route. This additional information may be requested, forexample, by the operator touching, tapping, or otherwise providing inputto the map and/or the listing areas in GUI 300. In the disclosedexamples, the operator has touched the Big J Coffee listing in GUI 300,causing the exemplary GUI 400 of FIG. 4 to be displayed.

GUI 400 may provide a zoomed-in view of a portion of the map from GUI300, as well as directions and/or a proximity value corresponding to theselected location. It is contemplated that the zoomed-in view and/or theother details from GUI 400 could additionally or alternatively beautomatically shown to the operator based on proximity of servicevehicle 12 to the particular location, if desired. For example, whenservice vehicle 12 is detected to be within a threshold distance (e.g.,about 0.5 miles) of the next stop in the assigned route, the disclosedapp may automatically cause GUI 400 to be shown.

It should be noted that the operator may be able to manually select aparticular stop out of sequential order from the assigned route toservice next, if desired. That is, the operator could override inputdevice 40 and choose a stop (e.g., by touching, tapping, or providingother input to device 40) that is not listed as the next stop in theprovided sequence. The operator may do this, for example, when bed 16 isnearly full and the stop listed next in the route would overfill bed 16.In this example, the operator may choose instead to visit a stop knownto have a lesser amount of waste that could be handled by servicevehicle 12 without overfilling bed 16. In another example, back office34 may override input device 40 and inform the operator via a dispatchcall of the need to go to the stop that is not listed next in theprovided sequence. This may occur, for example, in urgent or emergencysituations. Regardless of the reason for the out-of-sequence stop, oncethe out-of sequence stop is selected by the operator to be the nextstop, the app providing GUIs to input device 40 may be able toaccommodate the out-of-sequence stop and cause GUI 400 to providedirections and/or detailed information to the out-of-sequence stop.

The disclosed app may provide for manual confirmation of service vehicle12 stopping at an intended service location. For example, based on anamount of detected motion, a detected speed, a detected location, adetected use of lift arms 24, a detected force, a detected change in bedweight, or another detected condition, controller 30 may determine thatservice vehicle 12 has stopped. In this situation, the disclosed app maybe configured to confirm that the detected stop corresponds with anintended stop in the assigned route, for example via a GUI 500 shown inFIG. 5. The operator may then have the option to confirm or deny thatthe stop is one of the intended stops listed in the assigned route. Insome embodiments, this feedback from the operator may be used toselectively activate other functions and/or features of service vehicle12. For example, in some embodiments, sensors 42 may only be activatedwhen the operator confirms that the detected stop is one of the listedstops.

While service vehicle 12 is at a particular stop in its assigned route,any number of different pieces of information about the stop and/orreceptacles 14 at the stop may be automatically and/or manually obtainedand entered into input device 40. FIGS. 6 and 7 depict differentexemplary GUIs 600 and 700, respectively, that are provided by thedisclosed app and used for this purpose. For example, upon arriving atthe particular stop, GUIs 600 and 700 may provide a way to identify thecorresponding receptacle 14 that should be serviced and/or to link thereceptacle's identity to a particular stop and/or service task. This mayinclude input device 40 displaying an identification number, a size, aconfiguration, and/or a picture of the receptacle 14 expected to be atthe particular stop, so that the operator of service vehicle 12 mayconfirm service of a correct receptacle 14 at a correct location.Alternatively, GUI 600 may allow the operator to manually supply thereceptacle information to input device 40. For example, the operator maytype into GUI 600 the identification number of the receptacle 14 foundat the stop, scan into GUI 700 an associated bar code, upload a photo,etc. In this example, if the entered receptacle information does notmatch expected information, an indication of the mismatch may bedisplayed via input device 40 to the operator, such that the operatormay remedy the situation.

Also, while service vehicle 12 is at a particular stop in its assignedroute, exemplary GUIs 800 and 900 of FIGS. 8 and 9, respectively, may beused to provide information about the service task being performed atthe stop. For example, a weight of any waste dumped from receptacle 14into bed 16 of service vehicle 12 at the particular stop may be recordedvia GUI 800. The weight may be recorded automatically (e.g., based oninput from sensors 42) or manually (e.g., based on an external scale atthe stop or built into the receptacle 14), as desired. GUI 800 may alsoprovide the option for the operator to adjust the information displayedon GUI 800 (e.g., to update a record or overwrite a pickup weight orvolume) and/or to report a problem. Via GUI 900, the operator may thenbe able to provide details regarding any problem experienced whenattempting to service receptacle 14. Exemplary problems reportable viaGUI 900 may include, among others, that receptacle 14 cannot be found,that receptacle 14 is inaccessible, or that other problems haveoccurred. Any information obtained via GUIs 800 and/or 900 may betransmitted to back office 34 and used to update the correspondingcustomer accounts.

FIG. 10 illustrates an exemplary GUI 1000 that may be shown when bed 16of service vehicle 12 is nearly full (e.g., full within a thresholdamount), based on detected and/or confirmed completion of a previouswaste service known to supersede travel to the landfill, based ondetected approach of service vehicle 12 to the landfill, and/or based onother similar factors. The fill level of bed 16 may be determinedautomatically (e.g., based on a number of stops completed and an assumedamount of material at each stop, based on a measured weight or volume,etc.) or manually (e.g., based on operator input). The threshold amountmay be associated with a known capacity of service vehicle 12, localregulations, or other factors known in the art. GUI 1000 may illustratea map and/or navigation information for assisting the operator to driveservice vehicle 12 to a particular landfill (e.g., to Landfill A) and/orto a particular location within the landfill (e.g., a locationcorresponding to a type of waste contained within bed 16).

Upon arriving at Landfill A and performing its assigned waste service(i.e., after dumping the contents of bed 16), GUI 1100 of FIG. 11 may bedisplayed. GUI 1100 may provide an indication of the weight of the wastecontents deposited at Landfill A, and a way for the operator to update astatus of the waste service. GUI 1100 may be similar to GUI 800, andallow the operator to also overwrite the weight of the deposited wasteand/or to report a problem (e.g., via GUI 900).

The interfaces illustrated in FIGS. 3-11 are exemplary only and areprovided to highlight certain aspects of the disclosed system. Otherviews and functionality are contemplated, as would be understood by oneof skill in the art. It will be apparent to those skilled in the artthat various modifications and variations can be made to the disclosedsystem. Other embodiments will be apparent to those skilled in the artfrom consideration of the specification and practice of the disclosedsystem. It is intended that the specification and examples be consideredas exemplary only, with a true scope being indicated by the followingclaims and their equivalents.

What is claimed is:
 1. A system for providing waste management app,comprising: a locating device disposed onboard a service vehicle andconfigured to generate a first signal indicative of a location of theservice vehicle; a mobile device having a sensor internal to the mobiledevice, the mobile device being disposed onboard the service vehicle,and wherein the sensor is configured to generate a second signalassociated with waste services being performed by the service vehicle; acontroller in communication with the locating device, the mobile device,and the sensor, the controller being configured to determine completionof waste services based on the second signal and to cause a graphicaluser interface to display on the mobile device, an indication of a wasteservice having been completed.
 2. The system of claim 1, wherein thesensor is an acoustic sensor.
 3. The system of claim 1, wherein thesensor is an accelerometer.
 4. The system of claim 1, wherein the secondsignal is a detected acoustic signature associated with the wasteservices being performed.
 5. The system of claim 1, wherein thecontroller is further configured to: receive manual input from anoperator of the service vehicle indicating performance of wasteservices; and determine completion of waste services based further onthe manual input.
 6. The system of claim 1, wherein the controller andthe locating device form portions of the mobile device.
 7. The system ofclaim 1, wherein the controller is further configured to cause thegraphical user interface to display instructions regarding each wasteservice on the mobile device.
 8. The system of claim 1, wherein thecontroller is further configured to: receive input from an operator ofthe service vehicle requesting additional information about a particularlocation; and cause the graphical user interface to responsively displaythe additional information on the mobile device.
 9. The system of claim1, wherein the controller is further configured to: track movement ofthe service vehicle based on the first signal; make a determination thatthe service vehicle is approaching a particular location at which wasteservices are to be performed; and in response to the determination,cause the graphical user interface to display information associatedwith the particular location on the mobile device.
 10. The system ofclaim 1, wherein the controller is further configured to: receive inputassociated with a receptacle found at the location at which wasteservices are to be performed; and cause the graphical user interface toresponsively display information associated with the input on the mobiledevice.
 11. The system of claim 10, wherein the input is at least one ofa manually-entered identification of the receptacle, an automaticallydetected RFID tag, an uploaded image, a scanned index, a measuredweight, or a problem report.
 12. The system of claim 1, wherein thecontroller is further configured to: make a determination that a nextwaste service to be performed by the service vehicle is unloading ofwaste material at a landfill; and cause the graphical user interface toresponsively display information associated with the landfill on themobile device.
 13. The system of claim 12, wherein the controller isconfigured to make the determination based on at least one of aproximity of the service vehicle to the landfill, or an amount of wastematerial in the service vehicle.
 14. The system of claim 12, wherein thecontroller is configured to make the determination based on manual inputreceived from an operator of the service vehicle.
 15. The system ofclaim 12, wherein the controller is further configured to: determine aweight change in the service vehicle while the service vehicle is at thelandfill; and cause the graphical user interface to responsively displaythe weight change on the mobile device.
 16. A method for providing awaste management app, the method comprising: receiving a signalassociated with waste services being completed from a sensor internal toa mobile device and disposed onboard a service vehicle; determiningcompletion of waste services based on the received signal; anddisplaying a graphical user interface on the mobile device to anoperator of the service vehicle, showing a location of the servicevehicle relative to a location at which waste services are to beperformed.
 17. The method of claim 16, wherein the signal comprises anacoustic signature associated with the waste services being performed,and further including causing the graphical user interface to display anindication of a waste service having been completed based on theacoustic signature.
 18. The method of claim 17, wherein the acousticsignature is associated with at least one of lifting, tilting, ordumping of a receptacle.
 19. A non-transitory computer readable mediumcontaining computer-executable programming instructions for performing amethod of providing a waste management app, the method comprising:receiving a signal associated with waste services being performed from amobile device disposed onboard a service vehicle; and causing agraphical user interface to display on the mobile device to an operatorof the service vehicle, an indication a waste service having beencompleted.
 20. The non-transitory computer readable medium of claim 19,wherein the signal comprises an acoustic signature associated with thewaste services being performed, the acoustic signature being associatedwith at least one of lifting, tilting, or dumping of a receptacle.